Promote agentic pair programming with moshcode - #101
Merged
Merged
Conversation
ThreatCrush Security Scan34 finding(s) HIGH/CRITICAL: 4 | MEDIUM: 26 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promote agentic pair programming as a practical PairUX use case. The homepage now links to a dedicated walkthrough showing how teammates share a live moshcode session, use read/writer roles, and review the terminal and running app together in PairUX.
The page explains moshcode terminal permissions and PairUX's host-approved remote control, includes a contractor-onboarding example, and links to app.moshcode.sh and the PairUX download page. It also has canonical metadata and a sitemap entry. A formatting-only cleanup of the existing OpenAccess descriptor fixes the repository's format check.
Validation: all repository pre-commit checks passed (lint, typecheck, format, 2,038 package tests, 34 script tests, and builds). Desktop and mobile browser checks passed for the homepage link, new page, canonical metadata, and layout, with no JavaScript errors.
The nonblocking dependency audit reports existing Next.js advisories and also fails on the unchanged master commit 45a7039. This change does not modify dependencies or the audit workflow.